Selecting the type of visual marks in data visualizations based on user-selected visual properties of the marks

ABSTRACT

A method displays a graphical user interface for a data visualization application. The user interface includes shelves for specifying data visualization characteristics for a dataset. The method selects a map view based on geographic location field name(s) placed onto the shelves, and displays a geographic map. A user selects a visual encoding by placing a first field name onto a first shelf, which specifies a visual property of displayed marks. The property for each mark is determined by values of the first field in records of the result set. A mark displays for each record in the result set. When the first shelf specifies color of marks, each displayed mark fills the respective geographic region with a color based on the value of the first field. When the first shelf specifies size of marks, point marks are displayed with a respective size corresponding to the value of the first field.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/214,818, filed Jun. 22, 2008, entitled “Methods and Systems ofAutomatically Generating Marks in a Graphical View,” which is herebyincorporated by reference in its entirety.

This application is related to U.S. patent application Ser. No.11/005,652, filed Dec. 2, 2004, entitled “Computer Systems and Methodsfor Visualizing Data with Generation of Marks,” now U.S. Pat. No.7,800,613, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The disclosed embodiments relate generally to generating graphical viewsof data, and more specifically to automatically generating marks in agraphical view.

BACKGROUND

Graphical views provide user-friendly ways to analyze how data varieswith respect to one or more parameters. In some graphical views,variation of data with respect to one or more parameters is illustratedby varying one or more visual properties of marks that correspond torespective data points. For example, marks that cover respectivespecified areas in a graphical view, which are referred to as areamarks, may have colors or patterns that vary based on values ofcorresponding data. In another example, point marks displayed atdistinct locations in a graphical view may have sizes that vary based onvalues of corresponding data. Sometimes a “graphical view” is referredto as a “data visualization.”

Map views provide an intuitive way to examine geographical variation ofdata. Two common examples of map views are choropleth maps, which arealso referred to as filled maps, and proportional symbol maps. Forchoropleth maps, the marks are colors or patterns used to fillrespective geographical regions; these marks are examples of area marks.For proportional symbol maps, symbols displayed at respectivegeographical locations vary by size in proportion to values of aparameter at the respective geographical locations or correspondingregions. These symbols are examples of point marks. A map view is onedata visualization type. Other data visualization types include charts,such as bar charts.

There is a need for user-friendly software to generate graphical viewsof data, such as map views. In particular, a user may desire toassociate data with one or more visual mark properties and in responsehave appropriate symbols be displayed automatically. The user also maydesire to modify the association of data with visual mark properties andhave the graphical view update automatically.

SUMMARY

In some embodiments, a computer-implemented method of generating marksin a graphical view includes receiving a first user request to associatea first field name with a first visual mark property. In response to thefirst user request, area marks are displayed in a graphical view.Respective area marks correspond to respective values of a first fieldcorresponding to the field name. A second user request is received toassociate the first field name with a second visual mark property. Inresponse to the second user request, point marks are displayed in thegraphical view. Respective point marks correspond to respective recordsin a retrieved result set.

In other embodiments, a system for generating marks in a graphical viewincludes memory, one or more processors, and one or more programs storedin the memory and configured for execution by the one or moreprocessors. The one or more programs include instructions to receive afirst user request to associate a first field name with a first visualmark property and instructions to display, in response to the first userrequest, area marks in a graphical view. Respective area markscorrespond to respective records in a retrieved result set. The one ormore programs also include instructions to receive a second user requestto associate the first field name with a second visual mark property andinstructions to display, in response to the second user request, pointmarks in the graphical view. Respective point marks correspond torespective records in the retrieved result set.

In yet other embodiments, a computer readable storage medium stores oneor more programs for use in generating marks in a graphical view. Theone or more programs are configured to be executed by a computer systemand include instructions to receive a first user request to associate afirst set of data samples with a first visual mark property andinstructions to display, in response to the first user request, areamarks in a graphical view. Respective area marks correspond torespective data samples in the first set. The one or more programs alsoinclude instructions to receive a second user request to associate thefirst set of data samples with a second visual mark property andinstructions to display, in response to the second user request, pointmarks in the graphical view. Respective point marks correspond torespective data samples in the first set.

BRIEF DESCRIPTION OF THE DRAWINGS

The patent or application file contains at least one drawing executed incolor. Copies of this patent or patent application publication withcolor drawings will be provided by the Office upon request and paymentof the necessary fee.

FIG. 1 is a conceptual block diagram of an example dataset havingmultiple fields in accordance with some embodiments.

FIG. 2 is a conceptual block diagram of an example table generated froma dataset in accordance with some embodiments.

FIGS. 3A-3C are screenshots of a user interface for displaying map viewsin accordance with some embodiments.

FIG. 4 is a block diagram illustrating a computer system for generatinggraphical views in accordance with some embodiments.

FIG. 5 is a flow diagram illustrating a method of generating marks in agraphical view in accordance with some embodiments.

Like reference numerals refer to corresponding parts throughout thedrawings.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the subject matter presented herein. But itwill be apparent to one of ordinary skill in the art that the subjectmatter may be practiced without these specific details. In otherinstances, well-known methods, procedures, components, and circuits havenot been described in detail so as not to unnecessarily obscure aspectsof the embodiments.

To generate graphical views such as map views, a user first accesses adataset containing data to be analyzed. The dataset includes one or morefields, including fields with data to be analyzed and, in someembodiments, fields with corresponding geographical information. Thegeographical information specifies geographical areas (e.g., regions orlocations) corresponding to the data to be analyzed. For example, thegeographical information may include one or more of the followingfields: country; state or province; state or provincial capital; countyor parish; Metropolitan Statistical Area (MSA); Core Based StatisticalArea (CBSA); Designated Market Area (DMA); arbitrarily defined marketregion; school, congressional, or other district; address; city; street;street number; and ZIP code or other postal code. In some embodimentsthe geographical information is stored using Federal InformationProcessing Standards (FIPS) codes. Inclusion of fields specifyinggeographical areas allows data to be analyzed with respect to thespecified geographical areas, thus permitting the user to see variationof raw data, or of parameters calculated from raw data, across thespecified geographical areas. Geographical variation may be analyzedusing map views or any other appropriate graphical views (e.g., a barchart with separate bars for distinct geographical areas).

In some embodiments, the dataset includes location fields containingcoordinates associated with one or more geographical fields, to enablecreation of map views. For example, the location fields may specifylatitude and longitude values or any other set of coordinates capable ofbeing mapped. A dataset with location fields that contain coordinates issaid to be geocoded. If the dataset accessed by a user is not geocoded,the dataset may be geocoded by adding appropriate location fields.Alternatively, a result set generated by querying the dataset for datato be displayed in a map view may be geocoded by adding appropriatelocation fields to the result set. In some embodiments, location fieldsmay be added to the dataset or result set through a join operation witha table that includes coordinates for geographical areas listed in thedataset. For example, if the dataset or result set includes a “state”field, the dataset or result set may be geocoded by performing a joinoperation with a table that lists latitude and longitude values for eachstate (e.g., the latitude and longitude of the center of each state). Insome embodiments, location fields may be manually added to the datasetor result set.

The dataset may be stored in any appropriate arrangement and location.For example, the dataset may be stored in a table or in a databasecontaining multiple tables. The database may be stored locally orremotely.

FIG. 1 is a conceptual block diagram of an example dataset 100 havingmultiple fields 102 through 118 in accordance with some embodiments. Thedataset 100 is shown as a single table for visual clarity but in someembodiments may correspond to multiple tables in a database or to anyother appropriate arrangement. The dataset 100 includes records 122-1through 122-12 listing data for a hypothetical coffee business withstores throughout the country. Each record 122 corresponds to aparticular store, as specified by a store ID 102, and a particular typeof coffee 118 (e.g., regular or decaf). Each record 122 includes aninventory 116 for a type of coffee at each store and includes severalfields of geographical information, such as the city 104, state 106, ZIPcode 108, and geographical market 114 for each store. In addition, thedataset 100 is geocoded: each record 122 includes latitude and longitudefields 110 and 112 for the corresponding store. In addition to thefields 102 through 118 shown in FIG. 1, the dataset 100 could includeother fields. For example, the dataset 100 could include additionalbusiness data (e.g., sales and profits) for each combination of store102 and coffee type 118 and additional fields of geographicalinformation (e.g., street and street number of each store). The dataset100 also could include additional sets of latitude and longitude fields:for example, a first set of latitude and longitude fields could havevalues corresponding to cities listed in the dataset and a second set oflatitude and longitude fields could have values corresponding to stateslisted in the dataset.

To create a graphical view for analyzing the data in the dataset 100, aresult set 200 is generated from the dataset 100. In some embodiments,generating the result set includes aggregating data in the dataset 100.For example, a sum or average of inventory could be calculated bygeographical area (e.g., for each city 104, state 106, zip code 108, ormarket 114). The sum or average could be calculated for each coffee type118 or could be a total sum or average. A count of records for eachcombination of store ID 102 and a specified coffee type 118 could becalculated by geographical area, thus indicating the number of stores ineach geographical area. Maximum or minimum inventory levels per store ID102 could be calculated by geographical area. The result set 200corresponds to one or more fields, such as the inventory field 116, inthe dataset 100.

To perform these or similar calculations, the dataset 100 is queried andthe relevant data is retrieved from the dataset 100 in response to thequery. In some embodiments, the retrieved data is processed bygeographical area, as specified by the user. If a map view is to begenerated, the relevant latitude 110 and longitude 112 values also areretrieved or otherwise added to the result set. In some embodiments, ifthe dataset 100 includes a single relevant record for each specifiedgeographical area, raw data from the dataset 100 may be displayed in amap view. Therefore, in some cases, the result set 200 is just aselection of fields from the dataset 100. In some cases, correspondinglatitude 110 and longitude 112 fields are added to the result set 200 byjoining the dataset with another table.

FIG. 2 is a conceptual block diagram of an example result set 200containing data from the dataset 100 in accordance with someembodiments. The result set 200 (which is a table), is generated inresponse to instructions to sum the inventories 116 listed in thedataset 100 by state 106 and coffee type 118. The result set 200includes fields specifying the state 202 and coffee type 210, a fieldcontaining the total inventory 208 for each combination of state 202 andcoffee type 210, and corresponding latitude and longitude fields 204 and206 for the state 202. The result set 200 includes records 220-1 through220-10 for the various combinations of state 202 and coffee type 210.The latitude and longitude fields 204 and 206 may be generated from thedataset 100 or separately added to the result set 200 (e.g., using ajoin operation with a table that includes coordinates for states).

FIG. 3A is a screenshot of a user interface (UI) 300A for displayinggraphical views such as map views in accordance with some embodiments.The user interface 300A enables the user to specify a result set 200 tobe generated from the dataset 100 and to specify how to display theresult set in one or more map views 320. The UI 300A includes user inputfields for specifying the characteristics of a desired datavisualization, including what data will be displayed and how the datawill be displayed. In some embodiments, the user input fields arereferred to as “shelves” or “user input regions.” To avoid confusionwith “fields” in a dataset or result set, the terms “shelf” and“shelves” will be used when referring to a user input field in a userinterface.

As illustrated in FIGS. 3A-3C, various field names may be placed ontothe shelves, such as the field name “type” 210 on the columns shelf 302in FIG. 3A and the “State” field name 202 on the level of detail shelf314 in FIG. 3A. In addition, some embodiments allow a user to place anexpression or formula onto a shelf, such as the expression“SUM(Inventory)” 208 on the size encoding shelf 312 in FIG. 3A and theexpression “SUM(Profit)” 364 on the size encoding shelf 312 in FIG. 3C.Expression can use various combinations of field names and aggregationoperators such as SUM. As illustrated in FIG. 2, an expression using oneor more field names from the dataset 100 may create a field in theresult set 200 (e.g., SUM(Inventory) 208). Because of this, the term“field name” may be used to identify individual fields in the dataset100, an expression that includes one or more field names from thedataset 100, or to identify fields in the result set 200 (which may becomputed based on an expression).

In some embodiments, the UI 300A includes a “columns” shelf 302, a“rows” shelf 304, and a “level of detail” shelf 314. The UI 300A alsoincludes shelves for specifying visual properties of marks to bedisplayed in the one or more map views 320, including a mark text shelf308, color shelf 310, and size shelf 312. In some embodiments, the UI300A also includes a mark shape shelf (not shown), mark pattern shelf(not shown), mark edge/boundary shelf (not shown), and/or markorientation shelf (not shown). Each of these shelves corresponds to aparticular mark visual property. The term “visual property” as usedherein does not encompass mark type (e.g., whether a mark is displayedas a point or as a filled area). In some embodiments, the visualproperty shelves (e.g., shelves 308, 310, and 312) are referred to as“encoding” shelves, and the process of assigning a field name to such ashelf is referred to as “visual encoding.”

Assigning x-axis mapping coordinates such as longitude 206 to thecolumns shelf 302 (which specifies the x-position of the marks) andy-axis mapping coordinates such as latitude 204 to the rows shelf 304(which specifies the y-position of the marks) indicates that a map view,as opposed to another type of graphical view, is to be generated.Additionally, adding coffee type 210 to the columns shelf 302 indicatesthat two map views 320-1 and 320-2 are to be generated, one for eachcoffee type (Decaf or Regular). Adding “SUM(Inventory)” 208 to the marksize shelf 312 specifies that the size of each mark is to correspond torespective values of “SUM(Inventory)” 208. Adding “state” 202 to thelevel-of-detail shelf 314 specifies that the “SUM(Inventory)” quantity208 is to be calculated on a per-state basis and that a separate mark isto be displayed for each state in the dataset 100.

The dataset 100 is queried based on the selections on the shelves tocreate a result set 200. One or more geographical maps is displayed inthe UI 300A, and marks are generated on the map(s) corresponding to theresult set 200. The geographical map(s) selected for display correspondsto the geographical area or areas specified on the level-of-detail shelf314. For example, in UI 300A, maps of the United States are displayed,because the field name “State” 202 is specified on the level-of-detailshelf 314.

A mark 322 is displayed for each state for which the dataset 100includes inventory data. The type of mark displayed in the map views320-1 and 320-2 is determined based on the contents of the shelves 308,310, and 312 for specifying mark visual properties. In the UI 300A, themarks are symbols, as determined by a rule that symbol marks are to bedisplayed when data is specified on the mark size shelf 312. Thisdetermination of mark type spares the user from having to specify marktype. Indeed, the user can generate appropriate map views withoutknowing about different mark types. The size of each mark 322corresponds to the expression “SUM(Inventory)” 208, which identifies afield 208 of the result set 200 and illustrated in the key 324. In thisexample, the size of each mark is proportional to the quantitySUM(Inventory), such that mark sizes increase with increasing values, asillustrated in the key 324.

In some embodiments, the user does not need to add longitude 206 to thecolumns shelf 302 or latitude 204 to the rows shelf 304 to specify thata map view is to be generated. Instead, if a geographical field name(e.g., “State” 202) is added to the level-of-detail shelf 314, thesystem determines that a map view is to be generated and automaticallyadds longitude 206 to the columns shelf 302 and latitude 204 to the rowsshelf 304. In some embodiments, whether a field is geographical isspecified in the schema of the dataset 100.

A user viewing the map views 320-1 and 320-2 (which are proportionalsymbol maps) may desire to transition to different map views. Forexample, the user may desire to transition from display of proportionalsymbol maps to display of choropleth maps (i.e., maps in which regionsare filled by colors or patterns), to transition from display of marksof varying size to marks of varying color, or simply to try an alternateview. To accomplish this transition, the expression “SUM(Inventory)” 208is removed from the mark size shelf 312 and added to the mark colorshelf 310, as illustrated in UI 300B. In response, the symbols 322 areremoved from the displayed map and replaced with fill colors 342 (e.g.,342-1 and 342-3 for California, and 342-2 and 342-4 for Florida),resulting in map views 340-1 and 340-2. The map views 340-1 and 340-2show choropleth maps with area marks 342, as opposed to the proportionalsymbol maps of map views 320-1 and 320-2 (FIG. 3A). The use of areamarks 342 is determined based on a rule that area marks are to bedisplayed when data is specified on the mark color shelf 310 and not onthe mark size shelf 312. The fill color of each mark 342 corresponds tothe quantity SUM(Inventory), as illustrated in the key 344. In thisexample, the fill colors 342 are shades of green with darknessproportional to the quantity SUM(Inventory), such that darker shadescorrespond to larger values.

Marks displayed in a map view may have multiple respective visualproperties that vary based on multiple respective fields or expressions.For example, a mark's color may vary based on a first expression and itssize may vary based on a second expression, as illustrated in the UI300C. The UI 300C follows from the UI 300B by leaving the expression“SUM(Inventory)” 208 on the mark color shelf 310, leaving “State” 202 onthe level-of-detail shelf 314, and adding the expression “SUM(Profit)”364 to the mark size shelf 312. This example assumes that the dataset100 includes a “Profit” field. In response, display of the marks 342ceases, a result set including the fields “SUM(Inventory)” and“SUM(Profit)” is created, and marks 362 are displayed in the map views360-1 and 360-2. The marks 362 are symbols with sizes that vary based onvalues of SUM(Profit) 364, as illustrated in the key 368, and colorsthat vary based on values of SUM(Inventory), as illustrated in the key366. The use of symbols for the marks 362 is determined based on a rulethat symbol marks are to be displayed when data is specified on the marksize shelf 312, regardless of whether or not data is specified on themark color shelf 310.

The UIs 300A-300C thus allow a user to transition between map views bymodifying the contents of mark specification shelves 308, 310, and 312,in response to which the type of mark to be displayed is selected basedon a set of rules. In some embodiments the UIs 300A-300C also enable auser to transition between a map view and another type of graphicaldisplay. For example, a user viewing the map views 320-1 and 320-2 inthe UI 300A may desire to view another type of graphical view (e.g., achart) of inventory by state instead. In some embodiments, thistransition is achieved by modifying the field names on the columns shelf302 and rows shelf 304 and/or on the mark specification shelves 308,310, and 312. For example, the user may delete longitude 206 from thecolumns shelf 302 and latitude 204 from the rows shelf 304, in responseto which the map views 320-1 and 320-2 are replaced with another type ofgraphical view. The shelves 302, 304, and 314 and shelves 308, 310, and312 thus may be used to generate both map views and other types ofgraphical views.

FIG. 4 is a block diagram illustrating a computer system 400 forgenerating graphical views in accordance with some embodiments. Thecomputer system 400 typically includes one or more processors 402, oneor more network or other communications interfaces 406, memory 404, andone or more communication buses 414 for interconnecting thesecomponents. The one or more network or other communications interfaces406 allow transmission and reception of data and instructions through anetwork connection. The communication buses 414 may include circuitry(sometimes called a chipset) that interconnects and controlscommunications between system components. The computer system 400 mayalso include interface devices 408, such as a display device 410 and auser input device 412. User interface images (e.g., UIs 300A-300C) maybe displayed on the display device 410 under the control of thegraphical view generation module 424, described below. Examples of userinput devices 412 include a keyboard, mouse, trackball, touchpad, ortouch screen. Memory 404 includes high-speed random access memory, suchas DRAM, SRAM, DDR RAM or other random access solid-state memorydevices, and may include non-volatile memory, such as one or moremagnetic disk storage devices, optical disk storage devices, flashmemory devices, or other non-volatile solid-state storage devices.Memory 404 may optionally include one or more storage devices remotelylocated from the processor(s) 402. Memory 404, or alternately thenon-volatile memory device(s) within memory 404, comprises a computerreadable storage medium. In some embodiments, memory 404 stores thefollowing programs, modules, and data structures, or a subset thereof:

-   -   an operating system 416 that includes procedures for handling        various basic system services and for performing        hardware-dependent tasks;    -   a network communication module 418 that is used for connecting        the computer system 400 to other computers via the one or more        communication network interfaces 406 and one or more        communication networks, such as the Internet, wide area        networks, local area networks, metropolitan area networks, and        the like;    -   a database 420 that includes one or more datasets 422 (e.g., one        or more datasets 100); and    -   a graphical view generation module 424 for generating graphical        views (e.g., map views) based on data from the one or more        datasets 422. In some embodiments, the graphical view generation        module 424 includes instructions to perform the method 500. The        graphical view generation module 424 is also referred to as a        “data visualization application.”

In some embodiments, the database 420 is stored externally to thecomputer system 400. For example, the database 420 may be stored on aserver in communication with the computer system 400 through a network.

In some embodiments, the data visualization application 424 includes adrawing module 426 for selecting and displaying a type of graphicalview; a mark generation module 428 for determining mark types,appearances, and locations and generating corresponding marks on agraphical view; and a database query module 430 for querying a dataset422 to generate a result set corresponding to one or more fields in thedataset 422.

In some embodiments, instructions corresponding to all or a portion ofthe graphical view generation module 424 are stored at and executed by aserver that transmits the results to the computer system 400 fordisplay.

Each of the above identified elements 416-430 in FIG. 4 may be stored inone or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules (or sets of instructions) may be combined orotherwise re-arranged in various embodiments. In some embodiments,memory 404 may store a subset of the modules and data structuresidentified above. Furthermore, memory 404 may store additional modulesand data structures not described above.

FIG. 5 is a flow diagram illustrating a computer-implemented method 500of generating marks in a graphical view in accordance with someembodiments. In some embodiments, the method 500 is performed at acomputer system 400 by executing instructions associated with the datavisualization application 424. Alternatively, some operations in themethod 500 are performed at a server in communication with the computersystem 400.

A first user request is received (502) to associate a first field namewith a first visual mark property. In some embodiments, the first visualmark property is (504) mark color. For example, in the UI 300B,“SUM(Inventory)” 208 is added to the mark color shelf 310, thusassociating “SUM(Inventory)” 208 with mark color. Alternatively, thefirst visual mark property may be mark pattern, such as the patternsused to fill respective marks.

In response to the first user request, area marks (e.g., marks 342-1through 342-4) are displayed (506) in a graphical view (e.g., map view340-1 or 340-2). Respective area marks correspond to respective recordsin a retrieved record set.

In some embodiments, the area marks include fill colors that correspond(508) to values of the respective field in the record set. For example,in UI 300B the shade of green for each mark 342 corresponds to the valueof SUM(Inventory) for the corresponding state. In general, variation ofcolor between respective marks corresponds to variation in the values ofa field in the record set, and may include variation in hue, saturation,and/or brightness. The various colors used for respective marks may bevarious shades of a single hue, such as various shades of graydetermined according to a grayscale that corresponds to values of thefield. For example, the darkness of the fill color may increase withincreasing data values. Alternatively, the darkness of the fill colormay decrease with increasing data values. Two or more hues could beused, with each hue corresponding to a distinct range of data values andthe darkness of each fill color increasing for increasing data valueswithin each range.

In some embodiments, the area marks include fill patterns thatcorrespond to respective data values. For example, distinct fillpatterns may correspond to distinct values. In another example, thedensity of the fill pattern may either increase or decrease withincreasing data values.

In some embodiments, the graphical view includes (510) a geographicalmap (e.g., the map of the United States in map view 340-1 or 340-2).

A second user request is received (512) to associate the first fieldname with a second visual mark property. In some embodiments, the secondvisual mark property is (514) mark size. For example, in the UI 300A,“SUM(Inventory)” 208 is added to the mark size shelf 312, thusassociating “SUM(Inventory)” 208 with mark size.

In response to the second user request, point marks (e.g., symbol marks322) are displayed (516) in the graphical view (e.g., the map views320-1 and 320-2). Respective point marks correspond to respectiverecords in the result set 200. In some embodiments, the point marksreplace the area marks displayed in operation 506.

In some embodiments, the point marks include symbols having sizes thatcorrespond (518) to values of the first field (corresponding to thefirst field name). In some embodiments, the symbols have sizesproportional to the field values. For example, sizes of the marks 322are proportional to values of SUM(Inventory) for respective states.Alternatively, the field values may be divided into ranges and the sizeof each symbol is determined by the range into which its value falls,with higher ranges having larger symbol sizes.

In some embodiments in which the graphical view includes a geographicalmap, records in the result set are associated with respectivegeographical values (e.g., respective values in the “SUM(Inventory)”field 208 are associated with respective states in the “State” field202). The area marks and point marks have display locations on thegeographical map that correspond to the respective geographical values.In some embodiments, the area marks have fill colors that correspond torespective values of the first field and the point marks include symbolshaving sizes that correspond to values of the first field.

In some embodiments, the second user request further associates a secondfield name with the first visual mark property, where the first visualmark property is mark color. In response, the symbols have colors thatcorrespond to values of the second field (corresponding to the secondfield name). In some embodiments, the first and second field namescorrespond to respective first and second fields in a dataset. Forexample, the request that associates “SUM(Inventory)” 208 with mark sizecould also associate “SUM(Profit)” 364 with mark color, resulting indisplay of map views with symbols for which size varies withSUM(Inventory) and color varies with SUM(Profit). FIG. 3C illustratessimilar map views, but with the data associations reversed: in FIG. 3C,“SUM(Inventory)” 208 is associated with color and “SUM(Profit)” 364 withsize.

In some embodiments in which the first field name corresponds to a firstfield of a dataset, the data corresponding to the first field name isgenerated from the dataset by querying the dataset (e.g., dataset 100)to retrieve data from the first field. In some embodiments, the firstfield is generated from the dataset by aggregating data in the firstfield with respect to associated geographical data (e.g., geographicaldata in a geographical field in the dataset, such as city 104, state106, zip 108, or market 114, FIG. 1). Aggregating data in the firstfield may include, for example, calculating sums (e.g., “SUM(Inventory)”208), averages, or counts of data in the first field for respectivevalues of the associated geographical data. In some embodiments, thefirst field is generated from the dataset by calculating, for respectivevalues of associated geographical data, maximum or minimum values ofdata in the first field. These options for generating the first fieldare also options for generating the second field.

The method 500 thus provides a user-friendly way to create graphicalviews without having to specify mark type explicitly. The method 500also allows easy transitioning between different graphical views,thereby simplifying data analysis. While the method 500 includes anumber of operations that appear to occur in a specific order, it shouldbe apparent that the method 500 can include more or fewer operations andthat an order of two or more operations may be changed. For example,operations 512 and 516 could precede operations 502 and 506.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method of selecting types of marks to use indata visualizations, comprising: at a computing device having one ormore processors and memory storing one or more programs for execution bythe one or more processors: displaying a graphical user interface,wherein the user interface allows a user to specify visualcharacteristics of a data visualization corresponding to a user-selecteddataset; selecting a map view data visualization type according to userselection of one or more geographic location fields from the dataset anduser association of the one or more geographic location fields with ashelf in the user interface that specifies level of detail for the datavisualization; in accordance with the selected map view datavisualization type, displaying a geographic map with predefinedgeographic regions corresponding to respective geographic locationsspecified by the one or more geographic location fields; receiving userselection of a first field from the dataset and user association of thefirst field with a first visual encoding shelf in the user interface,wherein the first visual encoding shelf specifies size of marks to bedisplayed; computing aggregated values for the first field based on theone or more geographic location fields; displaying a respective mark onthe geographic map for each computed aggregated value, wherein eachdisplayed mark comprises a point mark displayed at a respective locationwithin a respective geographic region and displayed with a respectivesize proportional to the respective computed aggregated value of thefirst field; receiving user association of the first field with a secondvisual encoding shelf that specifies color of the marks, replacing theuser association of the first field with the first visual encodingshelf; and in response to the user association of the first field withthe second visual encoding shelf, transitioning from display of thepoint marks to display of filled geographic regions, comprising:removing the point marks from display, and replacing each point mark byfilling the respective geographic region with a respective color havinga shade of darkness proportional to the respective aggregated value ofthe first field.
 2. The method of claim 1, wherein the computedaggregated values are computed using a formula selected from the groupconsisting of: summing values from the first field, computing an averageof the values from the first field, computing a maximum of the values ofthe first field, and computing a minimum of the values of the firstfield.
 3. The method of claim 1, wherein in response to user associationof the one or more geographic location fields with a shelf in the userinterface that specifies level of detail for the data visualization,fields corresponding to longitude and latitude are placed onto shelvesthat specify x-position and y-position of the marks.
 4. The method ofclaim 1, wherein the user interface includes a plurality of shelves forthe user to specify the visual characteristics of the datavisualization, and wherein the user specifies the characteristics byplacing field names associated with the dataset onto at least some ofthe shelves.
 5. A computer system for selecting types of marks used indata visualizations, comprising: one or more processors; memory; and oneor more programs stored in the memory for execution by the one or moreprocessors, the one or more programs comprising instructions for:displaying a graphical user interface, wherein the user interface allowsa user to specify visual characteristics of a data visualizationcorresponding to a user-selected dataset; selecting a map view datavisualization type according to user selection of one or more geographiclocation fields from the dataset and user association of the one or moregeographic location fields with a shelf in the user interface thatspecifies level of detail for the data visualization; in accordance withthe selected map view data visualization type, displaying a geographicmap with predefined geographic regions corresponding to respectivegeographic locations specified by the one or more geographic locationfields; receiving user selection of a first field from the dataset anduser association of the first field with a first visual encoding shelfin the user interface, wherein the first visual encoding shelf specifiessize of marks to be displayed; computing aggregated values for the firstfield based on the one or more geographic location fields; displaying arespective mark on the geographic map for each computed aggregatedvalue, wherein each displayed mark comprises a point mark displayed at arespective location within a respective geographic region and displayedwith a respective size proportional to the respective computedaggregated value of the first field; receiving user association of thefirst field with a second visual encoding shelf that specifies color ofthe marks, replacing the user association of the first field with thefirst visual encoding shelf; and in response to the user association ofthe first field with the second visual encoding shelf, transitioningfrom display of the point marks to display of filled geographic regions,comprising: removing the point marks from display; and replacing eachpoint mark by filling the respective geographic region with a respectivecolor having a shade of darkness proportional to the respectiveaggregated value of the first field.
 6. The computer system of claim 5,wherein the user interface includes a plurality of shelves for the userto specify the visual characteristics of the data visualization, andwherein the user specifies the characteristics by placing field namesassociated with the dataset onto at least some of the shelves.
 7. Anon-transitory computer readable storage medium storing one or moreprograms configured for execution by a computer system that includes oneor more processors and memory, the one or more programs comprisinginstructions for: displaying a graphical user interface, wherein theuser interface allows a user to specify visual characteristics of a datavisualization corresponding to a user-selected dataset; selecting a mapview data visualization type according to user selection of one or moregeographic location fields from the dataset and user association of theone or more geographic location fields with a shelf in the userinterface that specifies level of detail for the data visualization; inaccordance with the selected map view data visualization type,displaying a geographic map with predefined geographic regionscorresponding to respective geographic locations specified by the one ormore geographic location fields; receiving user selection of a firstfield from the dataset and user association of the first field with afirst visual encoding shelf in the user interface, wherein the firstvisual encoding shelf specifies size of marks to be displayed; computingaggregated values for the first field based on the one or moregeographic location fields; displaying a respective mark on thegeographic map for each computed aggregated value, wherein eachdisplayed mark comprises a point mark displayed at a respective locationwithin a respective geographic region and displayed with a respectivesize proportional to the respective computed aggregated value of thefirst field; receiving user association of the first field with a secondvisual encoding shelf that specifies color of the marks, replacing theuser association of the first field with the first visual encodingshelf; and in response to the user association of the first field withthe second visual encoding shelf, transitioning from display of thepoint marks to display of filled geographic regions, comprising:removing the point marks from display; and replacing each point mark byfilling the respective geographic region with a respective color havinga shade of darkness proportional to the respective aggregated value ofthe first field.